Wireless terminal

ABSTRACT

A system is described for managing data and information in a healthcare environment, such as a hospital. A handheld code scanner reads codes and either accepts data, or performs instructions based on the read code. The code scanner wirelessly transmits the codes or data to a central server which acts on the read code to carry out necessary functions. The system is useful for tracking patient data, such as for delivery of medicine. In addition, since the system can carry out instructions, it is useful for allowing healthcare workers to quickly and conveniently perform their duties without the necessity of sitting at a computer terminal.

CROSS REFERENCE TO RELATED APPLICATION

This application is a divisional of related U.S. application Ser. No.10/857,701 filed on May 28, 2004 and claims priority to U.S. ProvisionalPatent Application 60/475,173 entitled “MEDICAL MANAGEMENT SYSTEM” andfiled on May 30, 2003, U.S. Provisional Patent Application 60/530,073entitled “MEDICAL WORK FLOW SYSTEM” and filed on Dec. 16, 2003, and U.S.Provisional Patent Application 60/560,084 entitled “MEDICAL WORK FLOWSYSTEM” and filed on Apr. 7, 2004. The disclosures of theabove-described filed applications are hereby incorporated by referencein their entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to a system for controlling datain a health care environment. More particularly, the present inventionrelates to a medical processing system that includes a handheld scannerthat uses a code scanner for entering commands and data into a medicalmanagement system.

2. Description of the Related Art

Some computing tasks or environments require a high degree of mobility,ease of operation, and low cost implementation due to a large number ofusers. One example of such tasks is the administration and documentationof care provided to patients in a medical or hospital environment.Computer resources in these environments are limited due to inadequateavailability of access points such as input/output (I/O) stations orterminals. Although stationary terminals have a large screen, familiarfull-featured keyboard, and mouse input devices, such terminals areinconvenient to use in certain environments due to lack of portability,or availability due to cost and space constraints. Notebook computerswith wireless communication capabilities can increase the power ofcomputer terminals while maintaining relatively fast and availablecomputing power. However, they are still somewhat large in size, bulkyto transport, have limited battery life, require two hands to operate,and are expensive.

A plurality of small sized wireless computing devices have beendeveloped, such as wireless personal digital assistants (PDA's), for useby caregivers in administration and documentation of medical care. Forexample, U.S. Pat. No. 4,916,441 to Gombrich describes a handheldterminal that includes a wireless transmitter and a bar code scanner forentering medical data into a computer system. Unfortunately, a nurseneeds to manually type much of the information onto a small keyboard onthe device. This is inconvenient and time-consuming in a hospitalenvironment.

In addition, similar devices are either fragile or bulky, expensive, andrequire two-handed or tedious tasks for operation. Thus, improveddevices and methods are needed in the technology.

SUMMARY OF THE INVENTION

In one aspect of the present invention a wireless terminal for use inmedical care administration management system, comprising a code scannerconfigured to read scan codes, a processor configured to determinewhether the scan codes correspond to patient data or to an instructionand a wireless transceiver, configured to transmit the codes to a systemcomputer.

In some embodiments the system computer initiates a process in responseto receipt of a code corresponding to an instruction. In someembodiments the processor is further configured to determine whether theinstruction may be performed locally. The wireless terminal may befurther configured to execute the instruction. In another aspect of thepresent invention the terminal may be configured to store userinformation and transmit the user information with the codes read by thecode scanner to the system computer. In other embodiments the wirelessterminal may further comprise a display for displaying messages to auser. In other embodiments the wireless terminal may further comprise aninput button for receiving input from a user.

In another aspect of the present invention the transceiver is configuredto communicate with the system computer over a computer network. Thecode scanner may be configured to read two-dimensional machine readablecodes. In some embodiments of the present invention the code scanner isconfigured to read barcodes. In other embodiments of the presentinvention the wireless terminal further comprises an additional codescanner. In one embodiment of the present invention a wireless terminalfurther comprises a plurality of indicators. In some embodiments theplurality of indicators includes at least one of a visual indicator andan audio indicator. In some embodiments a scan code corresponds to abinary number comprising a plurality of bits, and wherein one of theplurality of bits indicates whether the scan code corresponds to data oran instruction.

A terminal for use in a medical care administration system, the terminalcomprising a code scanner configured to read a two-dimensional data dotencoding a scan code, wherein the scan code corresponds to data or aninstruction and a data processing module configured to determine whetherthe scan code corresponds to data or to an instruction and furtherconfigured to wirelessly transmit the scan code to a server computer.

In some embodiments the wireless terminal further comprises aninstruction processing module configured to process scan codescorresponding to instructions. In some embodiments the code scanner isconfigured to read the two-dimensional data dot from an array of datadots having a center to center spacing between adjacent data dots ofless than about 30 mm.

In another aspect of the present invention a wireless terminal for usein medical care administration management system, comprising, a codescanner, configured to read scan codes a processor and a wirelesstransceiver, configured to transmit the codes to a system computer,wherein the wireless transceiver is further configured to communicatewith a server periodically.

In some embodiments the processor is configured to determine whether thescan code is data or an instruction. In other embodiments the processoris further configured to determine whether to wait for a periodiccommunication session with the server before executing an instruction.In other embodiments the wireless transceiver is further configured totransfer at least one of the data and the instruction to the serverwithout waiting for a periodic communication session with the server. Insome embodiments the wireless terminal is configured for one-handed use.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described with reference to the accompanyingdrawings. In the drawings, like reference numbers indicate likeelements.

FIG. 1 is a block diagram of one embodiment of a medical managementsystem.

FIG. 2 is a block diagram of one embodiment of a server used in themedical management system shown in FIG. 1.

FIG. 3 is a perspective view of one embodiment of a wireless terminalaccording to one aspect of the invention.

FIG. 4A is a bottom view of the wireless terminal shown in FIG. 3.

FIG. 4B is a side perspective view of the wireless terminal shown inFIG. 3.

FIG. 5A is a block diagram of components within one embodiment of awireless terminal.

FIG. 5B is a block diagram of one embodiment of a plurality of modulescommunicating with the microcontroller of a wireless terminal.

FIG. 6 is a flowchart illustrating one embodiment of a method ofoperating a wireless terminal in the medical management system.

FIG. 7 is a flowchart illustrating one embodiment of a method ofoperating a wireless terminal during a communication session with theserver.

FIG. 8 is a flowchart illustrating one embodiment of a method ofoperating the server during a communication session with a wirelessterminal.

FIG. 9 is a flowchart illustrating one embodiment of a method ofoperating the server.

FIG. 10 is a flowchart illustrating one embodiment of a method ofoperating the information update module in the server.

FIG. 11 is a flowchart illustrating one embodiment of a method ofoperating the messaging module in the server.

FIG. 12 is an exemplary illustration of one embodiment of a MedicationWorksheet for use in a medical management system.

FIG. 13 is an exemplary illustration of one embodiment of aconfiguration report used to configure a wireless terminal.

FIG. 14A is perspective assembly view illustration of one embodiment ofa DOT scanner for use in a wireless terminal.

FIG. 14B is a cross-sectional view of the assembled DOT scanner of FIG.14A.

FIG. 15 is an illustration of an additional embodiment of a wirelessterminal.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Embodiments of the invention relate to a system and method employing awireless handheld terminal for management of medical care in anenvironment such as a hospital. The wireless terminal preferably has atleast one code reader, or scanner, used to read codes corresponding to,for example, patient identification, item identification, documentationcharacters and phrases, commands, and instructions. The codes arepreferably machine readable codes, including one and two dimensionaloptically readable codes such as bar codes, but can include radiofrequency identification (RF ID) devices or tags. The codes can beapplied to objects, cards, or placards throughout a hospitalenvironment. In one embodiment, each user can have a card, or codesheet,comprising that user's most commonly used codes. Thereby, the user onlyneeds to scan the codes on their codesheet to enter particular data, orcarry out specific instructions.

As described below, in addition to scanning in codes as data, the systemalso scans in codes that provide an instruction to the system. Byscanning in a plurality of codes, a user, such as a nurse, can sendmessages, page, print, process commands at a server, and order medicaltests. For example, in one embodiment, a nurse may need to page a doctorto the patient's location. In this embodiment, the nurse would scan thepatient ID bracelet, which includes a scan code sequence identifying thepatient. The nurse would then scan an instruction code, printed eitheron a placard or in the room, which provides the instruction “page thedoctor”. The scanned codes would be transmitted wirelessly to theserver, and the instruction would be executed at the server.

The server would query a database or lookup table of codes andinstructions for the scanned codes and determine that one of the scannedcodes corresponded to a “paging” instruction. The system would thenexecute instructions to identify the doctor to be paged based on thescan code corresponding to the identification of the patient, and thenpage the appropriate doctor to the patient's location. In oneembodiment, the system is linked to a hospital administration systemwhich stores the name of each patient, and the doctor for the patientthat is currently on-call. Thus, the wireless terminal not only providesthe function of reading data with the code scanner, but alsoadvantageously performs functions using the same code scanner.

The terminal preferably establishes communication with a server thatmaintains a database of codes and corresponding information or commandswhich it uses to process the codes received from the terminal via awireless communication link. The server is preferably in communicationwith additional devices via a network, such as a local area network(LAN), where the additional devices perform a variety of functions, suchas messaging, printing, or record keeping. The server is also configuredto communicate with the wireless terminal to provide requestedinformation or information in response to scanning of particular codes,such as codes corresponding to particular medications.

In one aspect of the invention, the wireless terminal has processingcapabilities such that it can process codes locally withoutcommunicating with the server, and thereby interacting with the userautonomously in certain capacities. The terminal communicates with theuser via indicators and a display screen, such as an LCD screen. Theterminal can also be adapted with audio indicators such as a beep toindicate a warning condition or a message awaiting acknowledgement. Theuser can acknowledge or respond to messages displayed on the screen withan acknowledgement or “OK” button on the terminal. As one example, anurse might scan in a code from a packet of Digoxin, which is a medicineto treat heart problems that should be administered only after an apicalpulse measurement has been taken by the nurse. Once the nurse scans thecode from the Digoxin packet, a processor in the terminal reads the codeand compares it with an internal list of codes. In this case, theterminal would recognize the code as requiring an apical pulsemeasurement, and would display a warning and request input from thenurse of the apical pulse. The nurse could then scan in the apical pulsemeasurement by scanning codes corresponding to the appropriate numbersin order to enter the pulse measurement into the terminal. Once thepulse measurement was entered, the terminal could transmit the entereddata to the server.

The codes used and maintained in the system are preferably in a “closed”symbology, such that only one code corresponds to a particularinstruction or piece of information. This ensures that the system doesnot receive duplicate codes which correspond to different instructionsor information. In certain embodiments, the codes are implemented as a2-D matrix, or DOT as described in International Publication No. WO02/07065, hereby incorporated by reference in its entirety. In oneembodiment, the physical DOT is 7 mm in diameter, and comprises 321white or dark hexagons. In another embodiment, the physical DOT isapproximately 5 mm in diameter, but less than 7 mm in diameter. In oneembodiment, a computer server can be configured to generate a 64 bitnumber, encrypt it, and algorithmically produce a 2-D DOT which uniquelyrepresents the encoded data. Where the system is implemented using theDOT symbology, the system can have additional capabilities such as themethods and systems described in International Publication No. 02/21794A2. As used herein, a “dot scanner” is configured to read the DOTsymbology.

The 2-D DOT advantageously permits high density placement of DOTS asexplained in Publication No. 02/21794 A2. The DOTS can be placedadjacent to one another in the same horizontal row or vertical columnwithout the data from one DOT interfering with the ability of a terminalto read an adjacent DOT. Thus, the DOTS can be arranged as an array ofDOTS. In one embodiment, a center to center distance between adjacentDOTS is approximately 20 mm and is less than 25 mm. In otherembodiments, the center to center distance between adjacent DOTS is lessthan about 10 mm, 15 mm, 20 mm, 30 mm, 35 mm, 40 mm, 45 mm, 50 mm, 55mm, 60 mm, 65 mm, 70 mm, 75 mm, 80 mm, 90 mm, or 100 mm.

Due to the vast number of data combinations made possible by the DOTsymbology, (18 billion billion), an entire medical management system canbe implemented using DOT's to represent all of the information andcommands desired in the system. Thereby, the possibility of confusionwith commonly used bar codes is eliminated. The system may, however, beimplemented with both DOT and bar code technology, where the terminalwould include both a bar code scanner and a DOT scanner. Such anembodiment is described below.

As used herein, “instructions” refer to computer-implemented steps forprocessing information in the system. Instructions can be implemented insoftware, firmware or hardware and include any type of programmed stepundertaken by components of the system.

As used herein, a “code which corresponds to instructions” or a “codecorresponding to an instruction” means a code that refers to, or isconverted into, one or more instructions to be carried out in thesystem. For example, a code “ABC123” might point to an instruction thatresults in a doctor being paged to a particular room. Codes and theircorresponding instructions can be stored in a database or lookup tableso that scanning in a code causes the terminal to lookup the code in thedatabase and retrieve its corresponding instruction, or set ofinstructions. As described, codes are preferably converted into 1D or 2Dsymbols so that they can be conveniently scanned into the system.

One example of a Local Area Network may be a corporate computingnetwork, including access to the Internet, to which computers andcomputing devices comprising the system are connected. In oneembodiment, the LAN conforms to the Transmission ControlProtocol/Internet Protocol (TCP/IP) industry standard. In alternativeembodiments, the LAN may conform to other network standards, including,but not limited to, the International Standards Organization's OpenSystems Interconnection, IBM's SNA, Novell's Netware, and Banyan VINES.

As used herein, a “microprocessor” may be any conventional generalpurpose single- or multi-chip microprocessor such as a Pentium®processor, a 8051 processor, a MIPS® processor, a Power PC® processor,or an ALPHA® processor. In addition, the microprocessor may be anyconventional special purpose microprocessor such as a digital signalprocessor or a graphics processor. The microprocessor typically hasconventional address lines, conventional data lines, and one or moreconventional control lines.

As used herein, the term “module” refers to the various modules in thesystem as discussed in detail below. As can be appreciated by one ofordinary skill in the art, each of the modules comprises varioussub-routines, procedures, definitional statements and macros. Each ofthe modules are typically separately compiled and linked into a singleexecutable program. Therefore, the following description of each of themodules is used for convenience to describe the functionality of thepreferred system. Thus, the processes that are undergone by each of themodules may be arbitrarily redistributed to one of the other modules,combined together in a single module, or made available in, for example,a shareable dynamic link library.

The system may include any type of electronically connected group ofcomputers including, for instance, the following networks: Internet,Intranet, Local Area Networks (LAN) or Wide Area Networks (WAN). Inaddition, the connectivity to the network may be, for example, remotemodem, Ethernet (IEEE 802.3), Token Ring (IEEE 802.5), Fiber DistributedDatalink Interface (FDDI) or Asynchronous Transfer Mode (ATM). Note thatcomputing devices may be desktop, server, portable, hand-held, set-top,or any other desired type of configuration. As used herein, an Internetincludes network variations such as public internet, a private internet,a secure internet, a private network, a public network, a value-addednetwork, an intranet, and the like.

As used herein, the term “programming language” refers to anyprogramming language such as C, C++, BASIC, Pascal, Java, FORTRAN, andAssembly Language and ran under the well-known operating system. C, C++,BASIC, Pascal, Java, and FORTRAN are industry standard programminglanguages for which many commercial compilers can be used to createexecutable code.

System Overview

FIG. 1 is a block diagram of one embodiment of a medical managementsystem 10 implemented in a hospital environment. The system comprises acomputer or server 12, and a plurality of battery powered wirelessterminals 14A-D, wherein the wireless terminals 14 and server 12preferably communicate according to IEEE 802.11 wireless LANspecifications. The system can also use other wireless communicationsspecifications known in the technology, such as radio frequency (RF) orBluetooth. The system also preferably includes a hardwired terminal 16coupled to the server 12 via a network or direct connection, wherein thehardwired terminal 16 can be used as a control point for the system suchthat only authorized users can activate a terminal 14A, and as ahardwired communication link between a terminal 14 and the server 12.

The wireless terminals 14 and server 12 preferably communicateperiodically during communication sessions and are not in constantcommunication. Thereby, battery power at the wireless terminals 14 canbe conserved and situations where the terminal 14 is out ofcommunication range with the server 12 do not create power consumingloop processes wherein the terminal 14 continually attemptscommunication with the server 12. The server 12 and wireless terminals14, however, can communicate at any instant if desired, and are notlimited to communication during the designated communication sessions.The wireless terminals 14 are preferably small in size for ease ofportability and one-handed use.

The server 12 is also coupled to a plurality of peripheral devices andsystems, such as a printer 20, a messaging system 22, a pharmacy system24, a laboratory system 26, a hospital server 28, and a patient recordsystem 30, via a network connection. Commands or instructions receivedfrom the wireless terminals 14 are communicated by the server 12 to thevarious devices and systems for performance of requested tasks, andinformation from the various peripheral devices and systems arecommunicated to the wireless terminals 14 by the server 12. For example,the pharmacy system 24 can send updated medication information forpatients or send notification to the server 12 when a patient'smedication is ready. A terminal 14 can also query the pharmacy system 24for information via the server 12. Similarly, a terminal 14 can sendlaboratory test requests to the laboratory system 26, or receive testresults from the laboratory system 26 via the server 12.

Where the hospital server 28 maintains, for example, patientregistration information, the hospital server 28 can send updatedinformation to the server 12, and the wireless terminals 14 can updatethe hospital server 28, for example, when a patient has been discharged.

In one embodiment, the patient record system 30 is an Electronic MedicalRecord (EMR) system, and is updated with information from the wirelessterminals 14 so as to maintain an electronic record of each patient'smedication administration and any additional comments input to theterminal 14 by a user.

Thus, the wireless terminals 14 have capabilities similar to computerterminals which are connected to the peripheral devices and systemsthrough a conventional network. The interaction of the wirelessterminals 14, server 12, and peripheral devices and systems will bedescribed in further detail hereinafter.

The server 12 comprises a database 32 for storing a plurality of scancodes and each codes' corresponding data or instruction in order toperform a plurality of electronic tasks. The data includes, for example,information corresponding to a patient, medication, objects, and notetaking entries, and the instructions can include tasks such as “print apatient report”, “order laboratory tests”, and “request assistance”. Thedatabase 32 can be modified and maintained using the terminal 16 oradditional computer terminals in communication with the server 12. Incertain embodiments, the system comprises both a local server and aremote server, including local and remote databases. In suchembodiments, the local databases provide pointers to locate theappropriate remote server. In addition, where a plurality of servers anddatabases are used in a single hospital, for example, a master computeror server can be used to maintain and update the databases.

Server

FIG. 2 is a block diagram of one embodiment of the server 12, whereinthe server 12 is in data communication with transmit and receive, ortransceiver circuitry 46 including an antenna 48 for wirelesscommunication with the plurality of wireless terminals 14. The server 12may include additional transmit and receive circuitry for processing ofdata and instructions where the server 12 is linked to a wireless accesspoint including a transceiver and antenna. As described above, theserver 12 can also communicate with the wireless terminals 14 via ahardwired connection at the hardwired terminal.

The server 12 comprises a transceiver module 50 configured to receiveand facilitate transmission of data via the transceiver circuitry 46.The server 12 further comprises an activation module 54 configured toinitiate each terminal 14 at the beginning of each use. In oneembodiment, a user may request activation of a terminal 14 by scanning acode (or codes) corresponding to user information, such as a usernameand password. In one embodiment, the user scans an identification codeon their name badge, and thereafter enters a password into the codescanner. In response to an activation request, the activation module 54first verifies whether the user is authorized to use the terminal 14 byattempting to correlate the user information with information stored atthe database 32. Secondly, where a nurse at a nurse's station in ahospital is requesting activation of the terminal 14, the activationmodule 54 sends a list of tasks to be performed and information to beused by the nurse during their working shift. More specifically, whereNurse A requests activation of a terminal 14, the activation module 54sends information corresponding to Patients A, B, C, and D, who areassigned to Nurse A, to the terminal 14 along with any additional tasksto be performed by Nurse A for those patients or in general. Theseexemplary features of the system 10 are discussed in more detailhereinafter below in reference to FIGS. 12-13.

As shown in FIG. 2, the server 12 also comprises an analyze module 56 indata communication with the transceiver module 50 and configured toanalyze incoming data or instructions from the wireless terminals 14 viathe transceiver circuitry 46. The analyze module 56 is in datacommunication with additional processing and task performance modules atthe server 12, and communicates the incoming data or instruction to theappropriate module according to its analysis. As will be appreciated bythose skilled in the art, the server may include a separate analyzemodule or plurality of modules for analysis of data or instructions fromthe peripheral devices and systems and for analysis of data andinstructions from the wireless terminals 14.

The server 12 further comprises an instruction processing module 58 forprocessing an instruction, and a data processing module 60 forprocessing data, wherein analysis by the analyze module 56 determineswhether a communication from a wireless terminal comprises data or aninstruction, and sends the communication contents to the appropriatemodule for processing. The server 12 also includes a processor 62 and amemory 64, used by instruction processing and data processing modules58, 60 during operation. The memory 64 can also be configured to storethe database 32 of scan codes and corresponding instructions or data. Itshould be realized that additional memory types, such as a flash memory,can also be used to store data within the server 12.

The memory 64 is also configured to store information received from theperipheral systems for use by the wireless terminals 14 and their users.For example, where a server 12 is assigned to each nursing station in ahospital, the memory 64 stores information corresponding to the patientsassigned to the nursing station and the tasks to be performed by thecaregivers assigned to the patients. More specifically, the medications,time of administration, and any additional information regarding thecare of patient A is stored in memory 64 for use by the caregiverassigned to patient A.

The additional processing and task performance modules at the server 12comprise an information update module 66, configured to updateinformation stored in memory 64 with information from the plurality ofperipheral devices and systems. For example, the information updatemodule 66 receives medication orders from the pharmacy system, updatesthe memory 64 with the pharmacy orders, and sends updated medicationorders to the appropriate wireless terminal 14.

As shown in FIG. 2, the server 12 further comprises a report generationmodule 68 configured to coordinate generation of a report for aparticular patient or for all patients assigned to the user of theterminal 14 in response to an appropriate scan code instruction from aterminal 14. The report generation module 68 receives a reportgeneration instruction from the instruction processing module 58, anduses the processor 62 and memory 64 to obtain the information to beincluded in the report. Once the information has been gathered, thereport generation module 68 sends the report to the printer. This allowsa user to scan a particular code on the terminal in order to have apredefined report printed from the data stored on the server orelsewhere.

In one embodiment, the server 12 also includes a messaging module 70configured to receive, generate, and send messages to the wirelessterminals 14 and peripheral systems. The module 70 receives messagesfrom the messaging system 22 (FIG. 1) to be sent to the wirelessterminals 14. The messaging system 22 can include a computer terminal,or plurality of terminals, where a user can enter a text message to besent to a particular wireless terminal 14 by designating the user byname. For example, a text message comprising notification of an urgenttelephone call can be entered at the hardwired terminal 16 for Nurse A.The messaging system 22 communicates the message and correspondingterminal user identification (“Nurse A”, for example) to the server 12.The server 12 routes the message and user identification to themessaging module 70, which looks up the user identification (Nurse A) inthe database 32 or memory 64 to determine which terminal 14 shouldreceive the message. The messaging module 70 then formats the messagefor the destination terminal 14 and sends the message via thetransceiver module 50 and transceiver circuitry 46 to the terminalcontrolled by Nurse A.

In one embodiment, the report generation module 68 is configured togenerate a message to notify the user of the terminal 14 which requestedgeneration of a report that the report has been printed. The generatedmessage is communicated to the messaging module 70, which formats themessage and adds information for communication to the appropriateterminal 14.

In another embodiment, the patient record system 30 maintains anelectronic record for each patient with respect to medicationadministration, including, but not limited to, type of medication,quantity of medication administered, how administered, and time ofadministration. This information may then be stored at the server 12 andterminal 14, such that the server 12 may generate an alert ornotification message if a terminal fails to timely send data indicatingadministration of medication. Alternately, the terminal may generate analert or notification message if expected medication administration isnot received by the stored time of administration, or within apredefined time period prior to the specified time of administration.

For example, a patient may be scheduled for administration of aparticular medication at a predetermined time. The terminal 14 tracks anelapsed time after a predetermined medication administration time andmay generate an alert or notification message if no indication ofmedication administration has been received within a predetermined alerttime. The predetermined alert time may be, for example, 30 minutes orone hour after a scheduled administration time. Thus, the terminal 14may be configured to monitor for an event where the time elapsed sincethe scheduled time exceeds some predetermined latency time. The terminal14 may transmit the message to the server 12 for entry into thepatient's care record. The terminal 14 will continue to periodicallyalert the user of the terminal 14 until the user acknowledges the alertsor the expected information is entered at the terminal 14. The user ofthe terminal 14 may acknowledge the alert or notification by, forexample, selecting the “OK” button on the terminal 14.

Alternatively, the server 12 may send a message to a terminal 14 inresponse to some predetermined patient event. For example, a patient mayhave had one or more lab tests ordered to evaluate a condition. Theserver 12 may send a message to a terminal 14 in response to events suchas availability of lab results for a particular patient, changes inpatient medication, changes in patient health which may be monitoredmanually or through the use of telemetry, or some other predeterminedevent, such as a critical abnormal lab result.

In one embodiment, the server 12 maintains statistics on usage relatedto each individual terminal 14, the user, time information, and the typeof code (barcode or DOT, for example) read by the user during each coderead or scan event. In addition, information regarding, for example,mistakes in medication administration or user operation of the terminal,misreads of the code scanners, or other operational activity outside ofan ideal work flow is tracked by the server. Such tracking orcompilation of statistics provides for future performance improvementand optimization of the system.

Terminal

FIG. 3 illustrates one embodiment of the terminal 14. As shown, theterminal 14 is designed to fit comfortably in one hand of a user.Moreover, the features of the terminal 14 are positioned so that theuser can operate the terminal with one hand. An upper surface 71Aincludes a display 72, which is preferably a 3-line×16 character backlitliquid crystal display (LCD). The display 72 can be used to displaywarnings, prompts, messages, etc., for the user. Of course, theinvention is not limited to any particular type of display. Thus,display windows that show 1, 2, 4, 5 or more lines of text are withinthe scope of the invention. In addition, display windows that haveadditional features, such as chemiluminescent pigments, and non-textualdisplay properties, are within the scope of the invention.

The terminal 14 may also include indicators, such as a multiple ortricolor LED “Good Read” and message indicator 74 which, for example,illuminates briefly in green to notify the user when a code has beenproperly scanned, illuminates in red to notify the user when a code hasbeen improperly scanned, and illuminates in yellow to notify the userwhen a message has been displayed on the display 72. The terminal 14 mayalso include additional indicators, such as a power source indicator anda wireless connectivity indicator (not shown). Such indicators can beincorporated as part of the display 72, or can be separate LEDindicators which illuminate only when the available power is low or theterminal 14 is out of range for wireless connection with the server 12.In other embodiments, the one or more indicators may be one or moreLEDs. The indicators are not limited to the colors and functionsdescribed above. For example, an indicator LED may display red, yellow,or green, or combinations of these, depending on a status of theterminal 14.

Also located on the upper surface 71A is a DOT scan button 76 and abarcode scan button 77 to activate the code scanners, where theillustrated embodiment comprises both a DOT scanner and a barcodescanner. In the illustrated embodiment, the DOT scan button 76 ispositioned on the upper surface 71A opposite the location of the DOTscanner on a lower surface of the terminal 14, and the barcode scanbutton 77 is positioned on the upper surface 71A opposite the locationof the barcode scanner on the lower surface of the terminal 14 toindicate the location of the scanners to the user for scanning codes. Itwill be appreciated that in one embodiment a terminal comprises only abarcode scanner and barcode scan button, and in a second embodiment aterminal comprises only a DOT scanner and DOT scan button. The terminalmay additionally or alternatively include means for reading an RF IDtag.

As shown, the terminal 14 also includes an “OK” or acknowledge button 78for user input in response to questions, or to acknowledge messagesappearing on the display 72. Engaging the OK button 78 allows theterminal 14 to interact with the user in a predefined manner so thatinput from the user can be stored within the terminal 14, or transmittedto the server 12 for processing. It should be realized that othermechanisms for entering data into the terminal 14 are also contemplated.For example, a pair of “YES” and “NO” buttons could be implemented inplace of the single OK button 78. In addition, fewer or more buttonscould be placed on the rear surface, or other surfaces of the terminal14 without departing from the spirit of the invention. For example, theOK button 78 could be placed on a side surface and still be within thescope of the invention. In one embodiment, the terminal 14 includes ajog dial on a side surface of the terminal, for example, that can beused to scroll through messages that appear on the display 72, or toactivate one of the scanners 80, 81.

FIG. 4A is a bottom view of the terminal 14 and shows a lower surface71B which includes output windows for a bar code scanner 80 and a DOTscanner 81. Of course, embodiments of the invention include either feweror more output windows for scanning codes into the terminal 14. In oneembodiment, the terminal 14 only includes the bar code scanner 80. In asecond embodiment, the terminal 14 only includes the dot scanner 81.FIG. 4B is a side perspective view of the terminal 14 and shows theupper surface 71A and a portion of the DOT scanner 81.

FIG. 5A is a block diagram of one embodiment of the terminal 14. Asshown, the terminal 14 comprises the bar code scanner 80, DOT scanner81, display 72, LED indicator 74, DOT scan button 76, barcode scanbutton 77, and acknowledge button 78. The terminal 14 further comprisesa microcontroller 82, such as an Atmel AT91 16/32-bit microcontroller,which includes a processor 84. In one embodiment, the processor 84 has a32-bit reduced instruction set computer (RISC) architecture with a16-bit instruction set, for example, and is configured for low powerconsumption.

The microcontroller 82 further comprises memory, which may be acombination of a static random access memory (SRAM) 86 and flash memory88. The SRAM 86 is configured to store program and application data, andpreferably has a size capable of supporting a real-time operating systemand application data, as well as memory space for image processing usingdata from the DOT scanner. In one embodiment, the SRAM 86 issupplemented by a pseudo SRAM device 87, which combines a dynamic randomaccess memory (DRAM) cell structure with an SRAM interface, so as toprovide for low power consumption and low device cost. As will beappreciated by those skilled in the art, the single communication linesconnecting elements of the terminal 14 are exemplary in nature, and aplurality of communication or control lines are contemplated.

The flash memory 88 is configured for permanent storage of bootfirmware, operating system, driver, protocol stack, and applicationprogramming, and is also preferably configured for low power operation.In one embodiment, the flash memory 88 provides a relatively smallstorage amount, such as 2 Mbytes, and additional flash memory 90 isprovided external to the microcontroller 82. For example, an additional4 or 8 Mbytes of flash memory 90 is mapped into the memory area of themicrocontroller 82 using external interface or glue logic 92 for addressdecoding into the same bank as the flash memory 88. In one embodiment,the terminal operating system and/or application software at the flashmemory 88, 90 can be upgraded in whole or in part via a wirelesscommunication link.

The microcontroller 82 also comprises a plurality of interfaces forcommunication with a plurality of peripheral devices. In one embodiment,the microcontroller 82 further comprises an external bus interface 94configured to interface with the external memory components 87, 90 andglue logic 92, for example. The microcontroller 82 may also comprise aplurality of universal asynchronous receiver-transmitters (UART's) 96,97 configured for asynchronous communications with peripheral devices, aplurality of programmed input/output lines, and a programmedinput/output controller 98, configured to control the signals on theparallel input/output lines according to information from the processor84.

The terminal 14 may additionally comprise a supervisory chip 99 coupledto the processor 84 and including a reset function and a watchdog timer.The reset function facilitates a system reset, for example, when thevoltage supply rail exceeds a predefined threshold and maintains thereset condition for a predefined period of time while the terminal 14components are allowed to stabilize. The watchdog timer is coupled to awatchdog timer signal output from the processor 84, wherein the timerwill trip in the event of a software deadlock at the processor 84, andsubsequently initiate a system reset. In one embodiment, the terminal 14includes a clock 100 which provides the CPU clock, and the processor 84can be configured to reduce the clock rate to conserve power when in astandby or sleep mode. The clock 100 may include a clock synthesizer.The microprocessor 82 may also use the clock as a real-time clock inorder to communicate reminder messages or tones to the user forscheduled medication administrations or tasks. The clock can alsoprovide for time stamping of each code scanning event or other events atthe terminal 14. The terminal 14 may also include a real time clock,such as the Real Time Clock chip DS2415 from Maxim Semiconductor(Dallas), to provide the microcontroller 82 with real time information.

The glue logic 92 is preferably provided by a low power complexprogrammable logic device (CPLD), and is configured to interface withthe DOT scanner 81, a wireless communication transceiver 102, a displaycontroller 104, and a user input and indicator controller 106. Theterminal 14 may further include one or more antennas 108, coupled to thewireless communication transceiver 102. The DOT scanner 81 comprises animage sensor 120, such as an Omnivision OV6130 CMOS black and whiteimager incorporated into a digital camera including lens optics, and abright LED 122 for illumination of the DOT image for scanning. In oneembodiment, the DOT scanner 81 is a complete, individual unit and isconfigured to interface with the microcontroller 82 via the glue logic92.

The wireless communication transceiver 102 is configured to communicatewith the server 12 using wireless communication specifications such asRF, Bluetooth, or a WLAN specification, and the one or more antennas108. In one embodiment, the wireless communication transceiver 102 is awireless LAN (WLAN) module comprising a media access controller (MAC),such as the Agere WaveLAN WL 60010 MAC, and physical layer solution,such as the Agere WaveLAN WL 1141 802.11b Physical Layer Solution. TheMAC controller interfaces with the glue logic 92 via a compact flashinterface 124, and implements the 802.11 protocol specified by IEEEstandards. The WLAN module may also be configured to implement anadvanced encryption standard (AES). In one embodiment, the terminal 14further comprises an EEPROM 126, which is coupled to the transceiver 102and configured to store device information, such as productionattributes (serial number, board version, manufacturing date, MACaddress, production number, etc.) and radio calibration data.

The display controller 104 is configured to interface with the display72, which can be implemented with a black and white back-lit LCD. Forexample, the display 72 can be a 128×64 dot LCD module withchip-on-glass (COG) technology, or a 122×32 dot LCD module with tapecarrier package (TCP) technology. The graphic controller 104 can beimplemented, for example, with the Samsung Graphic Driver(KS0713/S6B1713). In one embodiment, the display controller 104 is notconfigured with built-in character fonts and a character font table isstored in memory in the terminal 14. The display controller 104 may beconfigured to display predefined symbols, such as a battery powerindicator, battery charge status indicator, wireless communicationstatus, and wireless communication signal strength.

In one embodiment, the user input and indicator controller 106 isconfigured to interface with one or more visual indicators, such as aplurality of single color LED's, bicolor LED's, or the tricolor LEDindicator 74, so as to facilitate activation or illumination of suchindicators according to control signals from the microcontroller 82. Theuser input and indicator controller 106 is further configured to monitorand receive input from one or more input switches or buttons, such asthe DOT scan button 76, the barcode scan button 77, and the acknowledgeor “OK” button 78. In one embodiment, the terminal 14 includes a jogdial switch to select and initiate the reading of a barcode or DOTimage. The user input and indicator controller 106 preferably interfaceswith the microcontroller 82 via the glue logic 92, wherein the gluelogic 92 extends general purpose input/output (GPIO) capabilities fromthe microcontroller 82. In addition, a de-bounce function may beprovided for the input buttons and the jog dial switch.

In one embodiment, the terminal 14 comprises one or more audioindicators, such as a piezo speaker 130 and driver 132, coupled eitherdirectly to the microcontroller 82 or through the glue logic 92. Theaudio indicator preferably provides acknowledgement to a user of asuccessful code reading and/or decoding of a barcode or DOT image, andmay also notify a user of a waiting message, alarm, or warning. Theaudio indicator may also produce different audio signals to indicatedifferent conditions to the user, such as a first audio signal toindicate a successful code reading and decoding, and a second, differentaudio signal to indicate an unsuccessful code reading and/or decoding.

The microcontroller 82 may include testing circuitry or one or moreinterfaces for testing circuitry at the terminal 14. In one embodiment,the microcontroller 82 comprises an embedded in-circuit emulator 134,and the terminal includes a joint test action group (JTAG) interface 136to support ARM standard embedded in-circuit emulation. The terminal 14may further comprise a debug port 138 for the microcontroller 82,comprising an RS232 transistor-transistor logic (TTL) interface tocommunicate with a peripheral test and debug monitor or circuit. Thedebug port 138 may also provide for initial programming of flash memoryin the terminal 14 through a built-in flash programming routine at themicrocontroller 82.

The terminal 14 further comprises the barcode reader 80, which may beimplemented with a modular barcode scan engine such as a miniaturized,high performance 650 nm laser-based, single-line decoded scan enginefrom Symbol Technologies (model no. SE-923). The scan engine ispreferably modular and self-contained, and includes a microcontrollerconfigured to decode a barcode into a format compatible with andreadable by the microcontroller 82. In one embodiment, the barcodereader 80 communicates with the microcontroller 82 through an RS232 TTLinterface via a slave microcontroller 140. The slave microcontroller 140is preferably configured for low-power operation, and acts as apass-through device when the barcode reader 80 is configured to decodebarcode data independently. In certain embodiments, the barcode reader80 is implemented with a scan engine which is not configured to decode abarcode, and the terminal 14 further comprises additional decoding orconversion circuitry configured to convert barcode data into anacceptable format for processing at the slave microcontroller 140.

In one embodiment, the terminal 14 comprises a battery monitor andsafety circuit 144 coupled to a battery power interface 146. The batterypower interface 146 is preferably configured to draw power from are-chargeable battery, such as a Li-Ion Polymer single cell battery,which provides approximately 3.7 volts. In one embodiment, the batteryand the battery monitor and safety circuit 144 are a single unit, andmay include the Texas Instruments chip BQ2050, for example. Where are-chargeable battery is used, the terminal 14 further comprises abattery charger interface 148 configured to interface the batterymonitor and safety circuit 144 with an external battery charger throughmetallic charger contacts, for example. The battery charger interfacemay be implemented, for example, with the Texas Instruments lithium ioncharger, part no. BQ24002PWP.

The battery monitor and safety circuit 144 is configured to monitor thepower level in the battery and conditions during charging, and the slavemicrocontroller 140 provides an interface, preferably a one wireinterface, between the microcontroller 82 and the battery monitor andsafety circuit 144. The battery preferably provides 3.3 volts forinput/output and 1.65 volts for the processor core power rails throughan on/off switch 149 for operation of the terminal 14. In oneembodiment, the terminal 14 includes one or more voltage converters 150,such as the Micropower Synchronous Buck-Boost DC/DC converter by LinearTechnology (LT3440EMS), to provide the desired power rails.

As the terminal 14 preferably remains operational for an extended periodof time, such as up to 12 hours, the terminal 14 is configured for lowpower operation. In one embodiment, peripheral components of the readerare not all operated simultaneously. For example, the terminal 14 ispreferably configured to refrain from transmitting and receiving data atthe wireless communication transceiver 102 at the same time a codereading event occurs at the DOT reader 81 or the barcode reader 80. Incertain embodiments, the wireless communication transceiver 102 mayconsume a large amount of power, and the specific transceiverimplemented, such as the Agere WaveLAN, provides a variety of powersavings modes that can be implemented to optimize the operational timeof the terminal 14 between battery re-charging events.

FIG. 5B is a block diagram illustrating one embodiment of a plurality ofmodules for implementation at the microcontroller 82. As will beappreciated by one skilled in the art, the following described modulesmay be implemented in conjunction with processors and storage devices inaddition to or in place of the microcontoller 82. As illustrated in FIG.5B, the microcontroller 82 comprises a scan module 160 configured toprocess the codes read by the code scanners 80, 81, and an analyzemodule 162, configured to analyze the processed scan codes. The analyzemodule 162 is configured to determine, for example, whether a scan codecorresponds to data or an instruction. If the analyze module 162determines that a scan code corresponds to data, the data scan code isprocessed at a data processing module 164. If the analyze module 162determines that a scan code corresponds to an instruction, then theinstruction scan code is processed at an instruction processing module166.

The data or instructions corresponding to the scan codes may be used orperformed locally at the terminal 14, or transmitted to the server 12via the communication transceiver 102. The microcontroller 82 mayinclude a transceiver module 168, which is configured to format data oran instruction for communication to the server according to thecommunication specifications of the communication transceiver 102. Asdiscussed above, the terminal preferably communicates with the server 12during designated communication sessions. During a communicationsession, the terminal 14 preferably transmits more than a single scancode from the terminal 14, however, the terminal 14 can transmit a scancode outside a designated communication session according to whether thedata or instruction is to be sent to the server immediately.Determination of whether data or instructions are to be transmittedimmediately may be based on user input or the type of data orinstruction.

The microcontroller 82 also comprises an activation module 170configured to operate in conjunction with the activation module 54 atthe server 12 when a user requests activation of a terminal 14.Following user authorization by the server 12, the activation module 170is configured to process information sent by the activation module 54 atthe server 12 and store the information in memory. In association withthe modules illustrated in FIG. 5B, memory will be referred to generallyand may include, but is not limited to, the SRAM 86 and Flash memory 88at the microcontroller 82, and the additional pseudo SRAM 87 and Flashmemory 90.

Referring to the example previously discussed, Nurse A requestsactivation of the terminal 14 by scanning a code on her identificationbadge. Upon authorization of Nurse A to use the terminal 14, which mayalso include input of a password at the hardwired terminal 16 or theterminal 14, the activation module 170 coordinates receipt ofinformation corresponding to Patients A, B, C, and D, who are assignedto Nurse A, along with any additional tasks to be performed by Nurse Afor those patients or in general. The activation module 170 then storesthe received information in memory. The activation module 170 alsostores the authorized user's identification code in memory, such thatdata and instructions sent to the server 12 can be tagged with theuser's identification for future use, for example, in record keeping. Inone embodiment, the terminal 14 communicates with the server 12 using ahardwired connection during an activation procedure.

The microcontroller 82 further comprises a display module 172 configuredto facilitate display of messages, text, and indicators on the display72 via the display controller 104. The microcontroller 82 also comprisesa user input module 174, configured to monitor and process user inputreceived at the OK button 78 and a keypad if included on the terminal14. The user input module 174 responds to the received inputaccordingly, for example, depending on the message being displayed onthe display 72.

The microcontroller 82 may further comprise an indicator module 176configured to control illumination of the Good Read and messageindicator 74, via the user input and indicator controller 106. Asdiscussed above, the indicators may include an LED configured forillumination, for example, to notify a user that the terminal 14 isawaiting acknowledgment of a message or has displayed a warning at thedisplay 72. The indicator module 176 may also be configured tofacilitate illumination of the Good Read indicator 74 when either of thescanners 80, 81 have scanned a new code. Where the terminal 14 includesan auditory indicator, the indicator module 176 is further configured tofacilitate activation of the auditory indicator, such as a beep or buzz,as a warning or to indicate that a code has been properly or improperlyread by one of the scanners 80, 81. The terminal 14 can include aplurality of auditory indicators, which can be downloaded, for example,from the server 12 via a hardwired or wireless connection.

The microcontroller 82 also includes a power management module 178configured to monitor remaining battery power via the battery monitorand safety circuit 14, and to schedule low power or no power operationof terminal components to conserve power. The power management module178 may also be configured to facilitate display of the amount ofavailable power or status of the battery via an indicator as discussedabove. The power management module 78 may be further configured tofacilitate communication of this information to the server 12. In oneembodiment, the microcontroller 82 further comprises an alarm andwarning module 180, configured to detect alarm and warning conditionsand generate alarm or warning messages for display at the display 72, oractivation of the indicators.

In the terminal 14 based embodiment of the alert system described above,the terminal 14 can further be configured maintain an electronic recordfor each patient with respect to medication administration, including,but not limited to, type of medication, quantity of medicationadministered, how administered, and time of administration. Themicrocontroller 82 may generate an alert or notification message if auser of the terminal 14 fails to timely indicate administration ofmedication. A user of the terminal 14 may timely indicate administrationof medication by, for example, reading the DOTs associated with thepatient and the medication. The microcontroller 82 may include ascheduling module 182 configured to manage scheduled tasks such asmedication administration times, to monitor user input indicatingcompletion of scheduled tasks or rescheduling thereof, and usernotification of scheduled tasks.

For example, a patient may be scheduled for administration of aparticular medication at a predetermined time. The terminal 14, uses aschedule monitoring function at the scheduling module 182 to track anelapsed time after a predetermined medication administration time andmay generate an alert or notification message if no indication ofmedication administration has occurred within a predetermined alerttime. As with the server based system, the predetermined alert time maybe, for example, 30 minutes or one hour after a scheduled administrationtime. Thus, the scheduling module 182 may monitor data entry for receiptof scan codes indicating administration of a medication or completion ofa task, for example, which correspond to scheduled medicationadministrations or tasks. In the event the scheduling module 182determines that the elapsed time following a scheduled medicationadministration exceeds some predetermined latency time, and no scancodes have been received to indicate completion of the scheduledmedication administration, the scheduling module 182 facilitatesactivation of an indicator or display of an appropriate message at thedisplay 72. The terminal 14 may continue to periodically display orsound the notification or alert until acknowledgement by the user of theterminal 14. The user of the terminal 14 may acknowledge the alert ornotification by, for example, selecting the “OK” button 78 on theterminal 14 or by performing the process associated with the alert. Theterminal 14 may present the alert on a display, using one or moreindicators, audibly, or using some other way or some other combinationof ways.

In one embodiment, the terminal 14 is configured to schedulenotification for a follow-up task in response to an event such asadministration of a medication or treatment. For example, in response toreceipt of user input indicating administration of a medication, thescheduling module 182 schedules a follow-up visit notification orreminder for the user to visit the patient and perform an additionaltask. In one particular example, a nurse may administer a painmedication and input corresponding information into the terminal 14. Inresponse to receipt of information regarding the administration of thepain medication, the scheduling module 182 schedules a notification fora predetermined time following administration of the medication, such asone hour. In addition, the notification may include instructions toperform an additional task or enter additional information, such aspatient heart rate or a pain score provided by the patient.Subsequently, the terminal 14 notifies the user, upon lapse of thepredetermined time, with instructions to visit the patient and perform apredetermined task or obtain and input predetermined information ordata, such as a pain score.

Processes

One embodiment of a method 198 of operating the terminal 14 isillustrated in the flowchart of FIG. 6. The process begins at a startstate 200, and then moves to a state 201 wherein the terminal 14receives a scan code using one of the scanners 80, 81. In a state 202,the terminal 14 determines whether the scan code corresponds to data oran instruction, wherein such a determination can be made according to asingle bit in the scanned code, for example. If the terminal 14determines that the scan code corresponds to data in state 202, theterminal 14 determines whether the data is the type of data expected ina state 204. For example, where the previous code scanned by theterminal 14 corresponds to a patient and the terminal was awaiting ascan code corresponding to a medication or note taking entry for thepatient, the wireless terminal would recognize that the current scancode corresponding to a different patient was not expected.

If the scan code is determined to correspond to an expected type of dataas determined in state 204, the terminal 14 determines whether to waitfor additional data in a decision state 208. If the terminal 14determines that it should wait for additional data in state 208, thewireless terminal waits to receive another scan code in state 201. Forexample, where a scan code corresponding to patient identification datawas received in state 200, the terminal 14 would await additional datafor the patient, such as the medication administered, dosage ofmedication, and note taking entries.

In the event the terminal 14 determines in decision state 208 that itshould not wait for additional data, it proceeds to a state 210 todetermine whether the scan code data corresponds to data stored inmemory. For example, where the authorized medications for Patient A arestored in memory, the terminal 14 determines whether the scan code datacorresponds to an approved medication for a designated patient as storedin memory. If the scan code data does not correspond to the data inmemory, the terminal 14 generates a warning to the user in a state 212,indicating that a code corresponding to an incorrect medication has beenscanned. The terminal 14 waits to receive another scan code in state201. The process 198 then moves to decision state 215 to determinewhether or not to display the warning to the user. If a warning is to bedisplayed, the process 198 moves to state 216 and displays the messageat the display 72. If a determination is made at decision state 215 thatno warning is to be displayed to the user, the process skips state 216and terminates at an end state 217.

However, if the scan code data does correspond to an authorizedmedication in state 208, the wireless terminal transmits the scan codedata to the server at the next communication session in state 214.Preferably, a plurality of scan codes are grouped together fortransmission to the server, wherein a group comprises a patientidentification code, a medication code, and a dosage. Depending on thetype of medication administered, the group may also comprise a patient'svital sign such as temperature, method of administration such as oral orinjection, and location of injection. Of course, embodiments of theinvention are not limited to particular groupings of data fortransmission to the server.

If the scan code is determined to correspond to an unexpected type ofdata as determined in state 204, the method 198 then moves to decisionstate 215 to determine if a message should be displayed to the user.There are several instances where the user should be provided withmessages. For example, where the terminal 14 is being used to documentand ensure accurate medication administration, the user first uses thewireless terminal to scan a code corresponding to a patient, such as acode on the patient's wristband. In response to such a code, theterminal 14 waits for additional data, and the user would proceed toscan a code on medication packaging. The wireless terminal 14 then usesthe patient identification code to determine whether the code from themedication packaging is an authorized code for the patient according tothe information stored in memory. In the event the scanned medicationcode corresponds to the authorized medication as stored in memory, theterminal 14 may display a message to indicate that the administration ofthe medication is authorized, dosage information, and administrationinformation. The terminal 14 can also display a prompt to the user forentry of additional information, such as patient pulse and/ortemperature. The user can enter such additional information, forexample, by scanning codes corresponding to numerical digits with theterminal 14.

Following administration of a medication, a caregiver can use theterminal 14 for documentation or note taking. In particular, the usercan document a reaction to a medication by scanning the appropriatecode. For example, in the event a patient vomits after receivingmedication, the user of the wireless terminal scans a code correspondingto the text “PATIENT VOMITED”. The terminal 14 recognizes that the codecorresponds to documentation data and transmits it to the server 12 withthe patient identification code during the next communication session.

Referring now back to decision state 202, if the terminal 14 determinedthat the received scan code corresponds to an instruction, the terminal14 proceeds to a decision state 218. In decision state 218, the terminal14 determines whether the instruction is to be performed by the terminal14 or to be sent to the server 12. If the instruction is to be performedby the terminal 14, the wireless terminal executes the instruction in astate 220. The process 198 then moves to the decision state 215 todetermine if a message should be displayed to the user.

If the instruction is to be sent to the server 12, the terminal 14proceeds to a decision state 222 to determine whether the instruction isan immediate instruction, i.e. the instruction needs to be sentimmediately and the terminal 14 should not wait for the nextcommunication session. If the terminal 14 determines that theinstruction is an immediate instruction in state 222, the terminal 14transmits the instruction to the server 12 immediately in a state 224and does not wait for the next communication session. If the wirelessterminal determines that the instruction is not an immediate instructionin state 222, the terminal proceeds to a state 226 to transmit theinstruction to the server 12 during the next scheduled communicationsession.

Thus, in one embodiment, the user of the terminal 14 scans a codecorresponding to an instruction to print a report or order a laboratorytest for a patient, sends a message or page, or requests informationfrom a peripheral system connected to the server 12 by scanning theappropriate code(s) with the code scanners 80, 81. The terminal 14 thenproceeds to transmit the instruction and any additional information,such as patient identification information, to the server 12 to initiatea procedure according to the instruction.

The terminal 14 can also initiate performance of an instruction, such asimmediate request for assistance. For example, a user can scan a code onthe wall in a patient room to request immediate assistance, wherein thecode includes information regarding the location of the code as scanned.Such an instruction would be determined to be an immediate instructionin state 222 and would therefore be transmitted to the server 12 withoutwaiting for the next communication session. In addition, the terminal 14is configured to execute instructions or commands such as displaymedication data for a patient, or recall and display the last N scancode entries.

Transmitting Data

FIG. 7 is a flowchart illustrating one embodiment of a method ofoperation of a terminal 14 during a communication session. In a state250, the terminal 14 transmits data and/or instructions to the server12. In a state 252, the terminal 14 receives data and/or instructionsfrom the server 12, and in a state 254, the terminal 14 updates memorywith the data received from the server 12. In a state 256, the wirelessterminal 12 performs the instructions received from the server 12, suchas display of a message on the display 72.

One embodiment of a method of operation of the server 12 during acommunication session with a wireless terminal is illustrated by theflowchart of FIG. 8. In a state 260, the server 12 receives data and/orinstructions from the terminal 14, and in a state 262, the server 12transmits data and/or instructions to the terminal 14. In a state 264,the server 12 updates memory 64 and the appropriate peripheral systems,such as the patient record system 30, with the data received, and in astate 266, the server 12 performs tasks or initiates performance of aprocess in response to instructions received from the wireless terminal14.

Processing Data and Instructions

One embodiment of a method 290 of operation of the server 12 in responseto receiving a scan code from a terminal 14 is illustrated in moredetail in the flowchart of FIG. 9. As illustrated in FIG. 9, the methodbegins at a start state 292, and proceeds to a state 300 wherein theserver 12 receives data and/or an instruction from the terminal 14 inthe form of a scan code. In a state 302, the server determines whetherthe scan code corresponds to data or an instruction. If the scan codecorresponds to data, the server 12 proceeds to a state 304 whereinmemory 64 is updated with the data. The server 12 may also send the datato the appropriate peripheral system such as the patient record system30.

If the scan code is determined to correspond to an instruction in state302, the server proceeds to a state 306 to determine whether theinstruction is to be performed by the server 12 or another device orsystem. If the instruction is to be performed by the server 12, themethod proceeds to a state 308 wherein the server 12 executes theinstruction. If the instruction is to be performed by a device or systemother than the server 12, the server 12 proceeds to a state 310 todetermine whether the instruction is to be performed by a peripheraldevice, such as the printer 20, or a system, such as the messagingsystem 22.

If the instruction is to be performed by a device, the server 12proceeds to a state 312 where the process is initiated in the designateddevice according to the instruction by either sending the instructiondirectly to the device, or modifying and formatting the instruction andsending a formatted instruction to the designated device. Followinginitiation of the process in the designated device, the server 12 mayquery whether the instruction has been performed or completed in a state314. If the instruction has not been performed, the server 12 caninitiate the process in the designated device again by returning tostate 312. If the instruction has been performed, the server 12 proceedsto an end state 316. In addition, the server 12 can send a message tothe terminal 14 notifying the user that the process initiated inresponse to the received instruction has been completed.

If the server 12 determines in state 310 that the instruction is to beperformed by a system, the server 12 initiates the appropriate processin the designated system or sends the instruction to the systemdesignated as part of the instruction. In a state 320, the server 12queries the system as to whether the instruction has been performed. Ifthe instruction has been performed, the server proceeds to an end state322, and if the instruction has not been performed the server returns tostate 318 and sends the instruction to the designated system again to beperformed. Alternately, if the instruction is in the process of beingperformed, or is waiting to be performed, the server 12 will continue toquery the system until the instruction has been performed. In addition,the server 12 can notify the user of the terminal 14 that sent theinstruction that the instruction has been performed by sending a messageto the terminal 14 for display.

Information Update Module

FIG. 10 is a flowchart illustrating one embodiment of a method ofoperation of the information update module 66 in the server 12. In astate 350, the server 12 receives an information update from aperipheral system or device, such as the pharmacy system 24, wherein theinformation received comprises updated medication orders for a patientor medication orders for a new or transferred patient. In a state 355,the information update module 66 stores the information in memory 64,and transmits the updated information to the appropriate terminal 14during the next communication session.

Messaging Module

One embodiment of a method of operation of the messaging module 70 inthe server 12 is illustrated in the flowchart of FIG. 11. The messagingmodule 70 receives information including a message for a terminal 14user in a state 370. In a state 375, the messaging module 70 looks forthe terminal user, designated by name or ID number, in memory 64 anddetermines which terminal 14 to send the message to according to userinformation for each terminal 14 stored in memory 64. In a state 380,the messaging module 70 transmits the message to the appropriateterminal 14 using the transceiver 46 and antenna 48.

The system 10 is also capable of additional processes, such as billingor inventory control. For example, every item given or used by a patientin a hospital has a scan code applied to it or that corresponds to it inthe system. When that item is used by or for the patient, the caregiverproviding the item scans the patient ID code and the item code. Suchinformation is then transmitted to a billing or record keeping systemfor future reference.

An additional capability of the system 10 may include entry of physicianorders for patients, where a physician uses a terminal 14 to entermedication or medical care orders for a patient by scanning codescorresponding to the patient identification information, the medicationto be administered, the dosage, and additional information regardingadministration of the medication.

Example Process

FIG. 12 is an example of a Medication Worksheet 1200 that may be used inconjunction with a terminal 14 and server 12, operating in a system suchas the hospital system 10 of FIG. 1, and using, for example, theprocesses of FIGS. 6-11. In one embodiment, a user such as a nurse,authorized personnel, or system administrator obtains a printed versionof the Medication Worksheet 1200 at the beginning of a working shift.For example, as previously discussed, the user of a terminal 14 may scana code corresponding to an instruction to print a Medication Worksheet,and then scan a code corresponding to data identifying the user. Inresponse to the instruction, the server 12 would facilitate printing ofthe Medication Worksheet for the identified user.

The Medication Worksheet 1200 comprises a number of fields supplying avariety of information. For example, the Medication Worksheet 1200 caninclude an assignment field 1210 that identifies the responsible user ornurse, applicable date, and applicable shift in terms of time. TheMedication Worksheet 1200 can also include a patient field 1220 thatidentifies one or more patients, their corresponding medications, andscheduled administration times for the medications.

The Medication Worksheet 1200 can also include fields comprising scancodes that a user such as a nurse or authorized personnel are likely touse during their working shift, such as medication administration sites.In one embodiment, the fields include a “sites” field 1230, an“override” field 1240, a “keypad” field 1250, and an “other” field 1260.

The “sites” field 1230 can include one or more scan codes associatedwith one or more medication administration sites or methods. Forexample, a user can administer medication to a first patient inaccordance with the schedule shown in the patient field 1220, whereinthe user scans a first patient scan code 1222 associated with the firstpatient. The user can then indicate, by scanning the appropriate scancode, the site at which a first listed medication was administered. Forexample, the user may scan the “1. thigh” scan code 1232 to indicatethat the first medication was administered via an injection to the leftthigh. The terminal 14 would then transmit the information correspondingto the scan codes, such as patient information, medication, and locationof medication administration, to the server 12. In response to receiptof the information from the terminal 14, the server 12 can thencommunicate the information to one or more modules or servers in thesystem, such as the patient record system 30.

The user can similarly scan a scan code in the “override” field 1240 toindicate a reason for overriding a scheduled administration ofmedication, such as “increased nausea”. The “keypad” field 1250 can beused to compose messages or enter data for transmission to a server 12,such as patient statistics including temperature. In FIG. 12, the keypadfield 1250 shows a numeric keypad. In other embodiments, the MedicationWorksheet 1200 may include a numeric, alphanumeric, symbolic,combination thereof, or some other keypad.

The “other” field 1260 can include other instructions or data entriesnot included in the previously described fields. For example, the“other” field 1260 may include a page scan code 1262 corresponding to aninstruction to “page S. Felner RN”, or other designated personnel thatmay be currently on duty. In response to a user scanning the page scancode 1260, the terminal 14 sends an instruction to the server 12, andthe server facilitates a page to the listed party. In addition, the usercan compose a message that is used in the page using the scan codes inthe “keypad” field 1250, or additional scan codes in the “other field1260 corresponding to predefined messages, such as “patient requestedconsultation”.

It may be advantageous to implement the scan codes on the MedicationWorksheet with DOTs to identify various inputs. Unlike a bar code, theDOTs consume a small area on a standard printed page and can bepositioned adjacent one another, both horizontally as well asvertically. The 2-dimensional nature of the dots allows the terminal 14to isolate and selectively read dots that are positioned very close toone another.

The system 10 can similarly use DOTs to initially configure a terminal14. FIG. 13 shows an embodiment of a configuration report 1300 that canbe generated and used to configure a terminal 14. A system administratoror other user can input information to the server 12, at the hardwiredterminal 16, for example, and can thereby facilitate printing of theconfiguration report 1300 by the printer 20 (see FIG. 1). The user canthen configure the terminal 14 using the information provided in theconfiguration report 1300, such as written instructions and a pluralityof scan codes implemented with DOTs, barcodes, or a combination thereof.

In one embodiment, the system administrator inputs a server address 1310and network address 1320 to the server 12. The server address can be,for example, an IP address. The system administrator can, for example,identify one of a plurality of server addresses using a pull down menu,manual entry, automated process or some other method of identifying aserver. Similarly, the system administrator can identify a network fromone or more available networks using a pull down menu, manual entry,automated process or some other method of identifying a server 12.

The server 12 can then process the information entered by the systemadministrator and generate one or more configuration scan codes 1330that can be used to configure the terminal 14. The one or more scancodes 1330 can include, for example, one or more DOTs that identify ordictate a configuration operation recognized by the terminal 14. One ormore additional scan codes may also be used to identify the serveraddress and network, as well as other communication protocol. In oneembodiment, the one or more scan codes in the configuration report 1300identify a Wired Equivalent Privacy (WEP) algorithm key that is used bythe terminal 14 to provide security over a wireless communicationchannel.

In order to configure a terminal 14 using the configuration report 1300,a user can simply sequentially read each scan code or DOT in theconfiguration report with the terminal 14. The terminal 14 is configuredonce all of the dots in the configuration report 1300 have been read bythe terminal 14.

Exemplary DOT Scanner

FIG. 14A is a perspective assembly view illustration of one embodimentof a DOT scanner 1400 for use in a wireless terminal 14. As illustratedin FIG. 14A, the DOT scanner 1400 comprises a flex circuit 1402 having aCMOS camera attached. A first positioning piece 1404 is coupled to theflex circuit 1402, and a shielding piece 1406 is positioned over theCMOS camera on the flex circuit 1402. A lens 1414 is inserted into alens sleeve 1410, and a lens retaining ring 1412 is coupled to the lenssleeve 1410 to retain the lens in the lens sleeve 1410. An outer sleeve1414 is positioned substantially surrounding the lens sleeve 1410 and isconfigured to focus the CMOS camera, via positioning of the lens withinthe outer sleeve 1414, such that a central viewing axis of the CMOScamera is perpendicular to a DOT over which the camera is positioned.The outer sleeve 1414 is positioned in a first narrow aperture 1416 of anose cone 1418, wherein the nose cone 1418 is configured to ensure theCMOS camera is positioned an optimal distance from a DOT during ascanning event. The nose cone 1418 also comprises a second opening 1420opposite the first narrow aperture 1416. The second opening 1420 has agreater circumference than that of the first narrow aperture 1416 and isconfigured to be positioned over and encircling a DOT for scanning. Thenose cone 1418 further comprises a second narrow aperture 1422positioned substantially adjacent to the first narrow aperture 1416, andconfigured to receive an LED 1424 and an LED sleeve 1426. The nose cone1418 is configured to focus light from the LED 1418 at the secondopening 1420 of the nose cone 1418 so as to illuminate a DOT during aDOT scanning event.

The assembled scanner 1400 is illustrated in more detail in FIG. 14B,where FIG. 14B is a cross-sectional illustration of the assembled DOTscanner 1400 of FIG. 14A. The configuration of the nose cone 1418 withrespect to the fist narrow aperture 1416 and the second narrow aperture1422 is more clearly illustrated in FIG. 14B, and a CMOS camera 1428 isvisible as coupled to the flex circuit 1402. As illustrated in FIG. 14B,the portion of the nose cone 1418 extending from the second narrowaperture 1422 merges with the portion of the nose cone 1418 extendingfrom the first narrow aperture 1416. Thereby, a DOT positioned at thesecond opening 1420 is illuminated by the LED 1424 positioned at thesecond narrow aperture 1422, while the CMOS camera 1428 captures animage of the DOT through the first narrow aperture 1416.

FIG. 15 is a top view illustration of an additional embodiment of aterminal 14. As illustrated in FIG. 15, the terminal 14 includes anumeric keypad 1520 for user input. The numeric keypad 1520 comprisesten numeric keypad buttons corresponding to the numbers zero throughnine, a decimal point button, and a backspace button. Alternately, thekeypad 1520 may be implemented in a configuration corresponding to thatused on a standard computer keyboard. As will be appreciated by thoseskilled in the art, the keypad 1520 can be implemented with a variety ofbutton combinations, and is not limited to the implementationillustrated and described herein. For example, the keypad 1520 may beimplemented with an alphanumeric keypad such as those used with astandard telephone keypad.

It will be appreciated that the above-described system can beimplemented in additional environments, such as nursing homes, etc. andis not limited to the health care industry. For example, implementationof the system in industries and environments where precise inventorytracking and workflow management can be advantageous.

The foregoing description details certain embodiments of the invention.It will be appreciated, however, that no matter how detailed theforegoing appears in text, the invention can be practiced in many ways.As is also stated above, it should be noted that the use of particularterminology when describing certain features or aspects of the inventionshould not be taken to imply that the terminology is being re-definedherein to be restricted to including any specific characteristics of thefeatures or aspects of the invention with which that terminology isassociated. The scope of the invention should therefore be construed inaccordance with the appended claims and any equivalents thereof.

1. A wireless terminal for use in medical care administration managementsystem, comprising: a code scanner configured to read scan codes; aprocessor configured to determine whether said scan codes correspond topatient data or to an instruction; and a wireless transceiver,configured to transmit said codes to a system computer.
 2. The wirelessterminal of claim 1, wherein said system computer initiates a process inresponse to receipt of a code corresponding to an instruction.
 3. Thewireless terminal of claim 1, wherein said processor is furtherconfigured to determine whether said instruction may be performedlocally.
 4. The wireless terminal of claim 3, wherein said wirelessterminal is further configured to execute said instruction.
 5. Thewireless terminal of claim 1, wherein said terminal is configured tostore user information and transmit said user information with saidcodes read by said code scanner to said system computer.
 6. The wirelessterminal of claim 1 further comprising a display for displaying messagesto a user.
 7. The wireless terminal of claim 1 further comprising aninput button for receiving input from a user.
 8. The wireless terminalof claim 1, wherein said transceiver is configured to communicate withsaid system computer over a computer network.
 9. The wireless terminalof claim 1, wherein said code scanner is configured to readtwo-dimensional machine readable codes.
 10. The wireless terminal ofclaim 1, wherein said code scanner is configured to read barcodes. 11.The wireless terminal of claim 1 further comprising an additional codescanner.
 12. The wireless terminal of claim 1 further comprising aplurality of indicators.
 13. The wireless terminal of claim 12, whereinsaid plurality of indicators includes at least one of a visual indicatorand an audio indicator.
 14. The wireless terminal of claim 1, wherein ascan code corresponds to a binary number comprising a plurality of bits,and wherein one of said plurality of bits indicates whether the scancode corresponds to data or an instruction.
 15. A terminal for use in amedical care administration system, the terminal comprising: a codescanner configured to read a two-dimensional data dot encoding a scancode, wherein the scan code corresponds to data or an instruction; and adata processing module configured to determine whether said scan codecorresponds to data or to an instruction and further configured towirelessly transmit said scan code to a server computer.
 16. Theterminal of claim 15 further comprising an instruction processing moduleconfigured to process scan codes corresponding to instructions.
 17. Theterminal of claim 15, wherein the code scanner is configured to read thetwo-dimensional data dot from an array of data dots having a center tocenter spacing between adjacent data dots of less than about 30 mm. 18.A wireless terminal for use in medical care administration managementsystem, comprising: a code scanner, configured to read scan codes; aprocessor; and a wireless transceiver, configured to transmit said codesto a system computer, wherein said wireless transceiver is furtherconfigured to communicate with a server periodically.
 19. The wirelessterminal of claim 18, wherein said processor is configured to determinewhether said scan code is data or an instruction.
 20. The wirelessterminal of claim 19, wherein said processor is further configured todetermine whether to wait for a periodic communication session with saidserver before executing an instruction.
 21. The wireless terminal ofclaim 18, wherein said wireless transceiver is further configured totransfer at least one of said data and said instruction to said serverwithout waiting for a periodic communication session with said server.22. The wireless terminal of claim 18 wherein said wireless terminal isconfigured for one-handed use.